Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1507

reference: 529-tree-1
name: 1507
tree-preservation-order: undefined
529-tpo-1
uprn
address-text
point: POINT (-1.014053 50.898425)
geometry: MULTIPOLYGON (((-1.013982 50.898418,-1.013986 50.898432,-1.013995 50.898444,-1.014011 50.898454,-1.014031 50.898461,-1.014052 50.898463,-1.014074 50.898461,-1.014094 50.898455,-1.014110 50.898445,-1.014121 50.898433,-1.014125 50.898419,-1.014121 50.898405,-1.014111 50.898392,-1.014096 50.898382,-1.014076 50.898376,-1.014054 50.898373,-1.014032 50.898375,-1.014012 50.898382,-1.013996 50.898391,-1.013986 50.898404,-1.013982 50.898418)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL